Systems and methods for driver authentication through embedded sensing

ABSTRACT

Systems and methods for driver authentication through embedded sensing are disclosed. In one embodiment, a system for driver authentication through embedded sensing may include a vehicle that may include a plurality of sensors, each sensor sensing at least one of a characteristic of a vehicle occupant and a movement of the vehicle occupant; at least one computer processor executing a computer application, the computer application receiving and processing data from the plurality of sensors; and a communication interface. The system may further include a back-end server in communication with the vehicle communication interface and a plurality of locations in communication with the back-end server. In one embodiment, the characteristic may be a biometric characteristic of the vehicle occupant.

This application is a Continuation of U.S. patent application Ser. No.14/555,083, filed Nov. 26, 2014, which is a nonprovisional applicationof U.S. Provisional Patent Application Ser. No. 62/024,398, entitled“Systems And Methods For Smart Vehicle Resident Mobile BankingApplications And Customized Biometrics Through Embedded Sensing,” filedJul. 14, 2014. It is also related to the following U.S. ProvisionalPatent Applications: U.S. Provisional Patent Application Ser. No.62/024,272, entitled “Systems And Methods For Transaction Pre-Fetching,Processing And Provisioning Through Intelligent Vehicle ElectronicSystem And Back-End Cloud Infrastructure”; U.S. Provisional PatentApplication Ser. No. 62/024,310, entitled “Systems And Methods ForSelf-Driving Or Self-Propelled Branch Automated Teller Machines ForSecure Banking Applications”; and U.S. Provisional Patent ApplicationSer. No. 62/024,407, entitled “Systems And Methods For PredictiveResource Allocation And Location Optimization For Self Driving BankBranch/ATMs.” The disclosure of each of these provisional applicationsis hereby incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention generally relates to systems and methods fordriver authentication through embedded sensing.

2. Description of the Related Art

Drive-through Automatic Teller Machines (ATMs) are commonly found in theUnited States and in other geographies. For routine bankingtransactions, a customer often drives to a bank, waits in thedrive-through ATM queue, and, when it is his turn, conducts thetransaction and is on his way.

SUMMARY OF THE INVENTION

Systems and methods for driver authentication through embedded sensingare disclosed.

In one embodiment, a system for driver authentication through embeddedsensing may include a vehicle that may include a plurality of sensors,each sensor sensing at least one of a characteristic of a vehicleoccupant and a movement of the vehicle occupant; at least one computerprocessor executing a computer application, the computer applicationreceiving and processing data from the plurality of sensors; and acommunication interface. The system may further include a back-endserver in communication with the vehicle communication interface and aplurality of locations in communication with the back-end server. In oneembodiment, the characteristic may be a biometric characteristic of thevehicle occupant.

In one embodiment, one or more of the plurality of sensors may be asensor that senses a movement of the vehicle occupant.

In one embodiment, each of the sensors may sense a different movement ofthe vehicle occupant, and the computer application extracts at least onefused motor skill from the plurality of sensed movements. The movementmay be associated with operating the vehicle.

In one embodiment, the locations may be an automated location or amanned location.

The vehicle may include a memory, and the memory may store a profile forthe vehicle occupant based on at least one of the sensed characteristicsof the vehicle occupant and the sensed movement of the vehicle occupant.

According to another embodiment, a method for establishing a driverprofile using a plurality of embedded vehicle sensors may include (1)receiving, from a first vehicle sensor in a vehicle, a sensed physicalcharacteristic for a vehicle occupant; (2) receiving, from at least onesecond vehicle sensor in the vehicle, a sensed movement for the vehicleoccupant; and (3) the at least one computer processor creating a userprofile from the sensed physical characteristic and the sensed movementdata. The user profile may be used to authenticate the user for atransaction.

In one embodiment, a plurality of second vehicle sensors each senses adifferent movement of the vehicle occupant, and the at least onecomputer processor may extract at least one fused motor skill from theplurality of sensed movements.

In one embodiment, the movement may be associated with operating thevehicle, with responding to a traffic situation, etc.

In one embodiment, the sensed physical characteristic and the sensedmovement data may be collected during operation of the vehicle.

In another embodiment, a method for authorizing a transaction mayinclude the steps of (1) retrieving a vehicle occupant profile for anoccupant of a vehicle; (2) receiving, from a first vehicle sensor in thevehicle, a sensed physical characteristic for the vehicle occupant; (3)receiving, from at least one second vehicle sensor in the vehicle, asensed movement for the vehicle occupant; (4) at least one computerprocessor comparing the sensed physical characteristic and the sensedmovement to the retrieved vehicle occupant profile; and (5)authenticating the driver by comparing the sensed driver data to thefused motor skill feature to the retrieved vehicle occupant profile.

In one embodiment, a plurality of second vehicle sensors may each sensea different movement of the vehicle occupant, and at least one computerprocessor may extract at least one fused motor skill from the pluralityof sensed movements.

In one embodiment, the movement may be associated with operating thevehicle, with responding to a traffic situation, etc.

In one embodiment, the step of comparing the sensed physicalcharacteristic and the sensed movement to the vehicle occupant profilemay include the at least one computer processor generating a sensedprofile from the sensed physical characteristic and the sensed movementdata are collected during operation of the vehicle.

In one embodiment, the sensed physical characteristic and the sensedmovement data may be collected during operation of the vehicle.

In one embodiment, the at least one computer processor may transmit theauthentication to a third party.

In one embodiment, the at least one computer processor may grant thevehicle occupant access to a vehicle wallet and may conduct atransaction with the vehicle wallet.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, the objectsand advantages thereof, reference is now made to the followingdescriptions taken in connection with the accompanying drawings inwhich:

FIG. 1 is a block diagram of a system for driver authentication throughembedded sensing according to one embodiment;

FIG. 2 is a flowchart depicting a method for driver authenticationthrough embedded sensing according to one embodiment;

FIG. 3 is flowchart depicting a method for creating a driver profilethrough embedded sensing according to one embodiment; and

FIG. 4 is flowchart depicting a method for driver authentication throughembedded sensing according to one embodiment.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Several embodiments of the present invention and their advantages may beunderstood by referring to FIGS. 1-4.

According to one embodiment, a driver's driving habits and patterns maybe used as a form of a biometric in order to authenticate a user toconduct a transaction, to enter a restricted area, etc. For example, theuser's fine/coarse motor skills, impulse responses, driving speeds,reactions, etc., may be collected and compared to a profile that thedriver has established.

While many drivers may like to use applications that requireauthentication while driving, is not easy—or sometimes even possible—toauthenticate users using mobile devices, PINs, passwords etc. as thismay distract the driver.

In one embodiment, vehicle sensors (e.g., cameras, voice recognition,weight sensors, pedal sensors, steering sensors, outside vehicle sensors(e.g., parking sensors, blind spot sensors, etc.), add-on devices (e.g.,safe driver devices for insurance purposes, etc.), etc. may be used toauthenticate the driver based on the user's personal biometrics (e.g.,retina/iris scan, voice recognition, facial biometrics, weight,fingerprints, etc.) and/or the driver's driving habits (e.g., speed,acceleration/deceleration patterns, steering habits (e.g., handpositions, etc.), hand writing on touch screen devices reactions,impulse response patterns, steering habits, following closeness,facial/eye movements, body position (e.g., position of left foot,whether the user likes to hold on to the gearshift, etc.), etc.).Driving data may be collected from, for example, steering wheel sensors,gas pedal sensors, manual transmission sensors, combinations thereof,etc.

In one embodiment, a combination of the vehicle data may be consideredtogether. For example, the data may be tied together temporally (e.g.,the driver's gas pedal behavior may be tied with the driver's clutchpedal behavior, etc.). From the integrated data, unique identifiers maybe extracted and a profile may be created. This profile may then be usedto authenticate the individual (e.g., driver or passenger) so that theindividual may conduct a transaction.

In one embodiment, the driver may be authenticated to use applicationsthat are associated with the vehicle (e.g., a mobile banking applicationrunning on the vehicle's systems). In another embodiment, the driver mayuse the vehicle's systems to authenticate the driver to use anapplication on the driver's electronic device (e.g., an application on asmart phone). In still another embodiment, the driver may beauthenticated to enter an area (e.g., a parking garage, a securefacility, etc.). In another embodiment, the driver may be authenticatedto conduct a transaction using a vehicle wallet, a wallet on thedriver's mobile device, etc.

In one embodiment, the driving biometrics may be combined with otherbiometric modalities to increase the reliability of the authentication.

In one embodiment, the driver profile may be used to authenticate theuser so the user may operate the vehicle.

In one embodiment, separate data may be maintained and verified for morethan one driver (e.g., a profile may be created for each family member,employee, etc.).

In one embodiment, the driver may be authenticated without an explicitauthentication stage by using data that may be collected through aprocess that may run in the background.

In one embodiment, a vehicle may be provided with a “vehicle wallet.”The vehicle wallet may be specific to the vehicle, and may reside in thevehicle's systems.

In one embodiment, the vehicle wallet may be dedicated to, or associatedwith a vehicle rather than an individual.

The vehicle wallet may comprise a mobile application component thatresides on the existing intelligent vehicle hardware and operatingsystem, a dedicated—trusted hardware processing unit, a trusted hardwaretoken, and/or any other components as necessary and/or desired.

In one embodiment, trusted hardware processing units and tokens may onlybe activated by acquiring the user's biometric information (e.g., facebiometrics, iris, voice, fingerprint, palm print, vein scans, weight,motion and other behavioral biometrics and a combination of any of theseor other biometrics).

The trusted hardware unit may then be used to perform desiredtransaction, such as financial/banking transactions, for the individual.These transactions may be fully encrypted.

In one embodiment, the vehicle may have multiple wallets for individualthat may be registered to, or associated with, the vehicle. For example,there may be a separate wallet for the owner of the vehicle, familymembers, user of a corporate vehicle etc. In one embodiment, more thanone individual may share a vehicle wallet.

In one embodiment, users of the vehicle system, such as drivers andpassengers, may use their respective vehicle wallets personally, maytransfer funds among them, may transfer funds to or from theirrespective vehicle wallets to a shared vehicle wallet or to anotherpersonal wallet, etc. Each individual using the system may have accessand communication to the back-end financial institution resources, suchas financial advisors, telepresence/conferencing capabilities, etc.

In one embodiment, a vehicle wallet may be linked to some or all of anindividual's banking information (e.g., profile, accounts, etc.). Inanother embodiment, the vehicle wallet may be weakly linked to some orall of the individual's banking information so that no one can determinethe individual's banking information from the vehicle wallet. In stillanother embodiment, the individual's banking information may not beconnected to the vehicle wallet.

In a corporate setting, the vehicle wallet(s) may be integrated with theinstitutions' travel and expense system. Individuals may have access toa vehicle wallet based on employee privilege, position, etc. and mayhave restricted budgets uploaded to the vehicle wallet for specifiedtypes of transactions, for specified type of routes of travel,anticipated travel distances, etc.

In one embodiment, car rental payments may be executed by the vehiclewallet, and the user may use the vehicle wallet to make a payment at thebeginning or end of the transaction. For example, the vehicle wallet maybe temporarily assigned to the user, and the payments may be made fromthe vehicle wallet.

In one embodiment, a number of actions may be taken using the vehiclewallet. For example, individuals may access banking accounts. transferfunds, withdraw cash, invest funds, make person-to-person payments amongpassengers, etc.

In other embodiments, an individual's account and/or vehicle wallet maybe used to make payments. The allocation among different accounts may berule-based. Certain types of accounts, users, etc. may be capped to amaximum amount. For example, in a restricted use case, they may havelimited access privileges.

In one embodiment, vehicles may make payments to stationary entities(such as pharmacies, drive through goods/services, tolls, parking, carregistration DMV payments, government institution drive through services(e.g., taxes, registration fee, post office, etc.), auto repair shops,etc.), drive through malls, gas stations, etc. using their vehiclewallets. In another embodiment, vehicles may make payments to anothervehicle, for example, through point systems or actual funds in avehicle-to-vehicle format. The system may be used to compensate othersfor minor accidents, certain traffic violations, pollution/carboncharges, ad valorem taxes, etc. should any apply.

In one embodiment, drivers may prepay for certain parking locations inadvance of an event.

In one embodiment, a vehicle may purchase driving information fromanother vehicle. For example, a vehicle may purchase informationregarding traffic, detours, gas prices, weather, etc. from anothervehicle that is traveling ahead of that vehicle, travelling in adifferent direction, taking a detour, etc. The system may use thisinformation to optimize or alter the vehicle's route, adjust vehicleenergy usage, purchase road images ahead of the road, provide warningsand alerts to the driver, change the handling/braking systemcharacteristics for bad weather conditions, etc. This information may beprovided to the vehicle control systems, both on-board and remote.

In one embodiment, vehicle wallets may interact with mobile bankingresources, such as Mobile ATMs and ATM Taxis for authentication, towithdraw cash, perform transactions, etc. through local communicationsor direct interactions with such vehicles.

This can also tie into a “point” system, where points can be earned fromcarpooling, safe driving and other user behavioral profile. The vehiclescan send points to each other in traffic, collect and use those pointslater on. For example, a user may purchase traffic information, detourinformation, construction, roadblocks, etc. from other drivers. Theinformation may be used to update a navigation system, etc. In oneembodiment, the vehicles may exchange points/data automatically, and thepoints may be used for other things, such as parking priority, etc.

In one embodiment, the vehicle wallet may be an application, part of anapplication, etc. The vehicle wallet may have separate settings forexample, for budget allocation across a group of users. Individuals mayhave different access privileges for shared wallets, individual wallets,etc. For example, parents may have different access privileges thanchildren to make payments using shared vehicle funds.

For example, different family members may use the vehicle wallet toallocate or use funds specific to themselves. Shared or common accountsmay be used for other purposes.

The vehicle wallet authentication system may process each driverseparately based on each driver's profile. Once the driver isauthenticated, the driver may access shared vehicle funds orpersonalized funds/accounts as necessary and/or desired.

In one embodiment, the driver may use the vehicle wallet to conducttransactions. For example, the driver may pay for goods/services atdrive-through vendors (pharmacies, dry cleaning, food, etc.), pay forparking, pay for fuel (e.g., through NFC or other communicationchannel), tolls, traffic fees, etc. In one embodiment, the vehiclewallet may be linked to a bank account, credit account, etc.

In one embodiment, a family may be authenticated and may share a singlevehicle wallet account dedicated to the vehicle.

In one embodiment, a vehicle wallet may be loaded through NFC, iBeacon,or any other suitable type of communication. In one embodiment, thecommunication may be from a smart phone that may be linked, for example,to a banking account, credit account, etc.). By creating a level ofseparation, the driver may pay anonymously and more securely through thevehicle wallet.

In one embodiment, passengers may make person to person payments throughthe vehicle wallet or the vehicle wallet system.

In one embodiment, the vehicle wallet and/or vehicle wallet applicationsmay have a range of privacy modes. For example, a private mode may notdisclose the driver's name, banking information, etc. to the otherparticipant in a transaction.

The vehicle wallet may be linked to a personal banking account, creditcard account, etc. Thus, the vehicle may function as the payment devicein certain situations.

In one embodiment, a driver may transfer funds via a driver's mobileelectronic device, from a mobile electronic device wallet, etc. In oneembodiment, the driver may send funds to, from, or through a mobileelectronic device wallet in the vicinity (e.g., a parent may send fundsto a driving teenager through the vehicle wallet).

In one embodiment, a shared vehicle wallet may provide multiple driversaccess to a shared vehicle wallet (e.g., a family, employees sharing acompany car, etc.). Each driver may have a specified level of access tothe resources in the vehicle wallet. In one embodiment, the driverand/or passenger(s) may be continuously authenticated through theintelligent vehicle trusted system. In one embodiment, if theauthentication fails, the connection to the system may be disconnected.

In one embodiment, the system may be deactivated and concealed undersome circumstances, due to security reasons, to protect from intruders,high risk conditions (e.g., night driving), etc.

In one embodiment, different drivers may be authenticated through PINs,passwords, biometrics, etc. In one embodiment, drivers may maintainseparate wallets, or may share a wallet that may be used to pay forfuel, drive through goods/services (e.g., food, retail, banking,pharmacy, etc.), parking, highway payments, car-to-car informationexchange payments, other purchases, etc. In another embodiment, a customcurrency may be used for vehicle-to-vehicle communications (e.g.,receiving info about traffic on the road ahead).

In one embodiment, additional security features throughcross-correlating driver and/or passenger information may be used. Forexample, if a non-authenticated driver on board, the vehicle walletapplication may operate in “private” mode, providing higher securitythan if the driver were alone or with authenticated persons.

In one embodiment, the driver may be provided with access to mobileapplications that may be customized to the driver, seat position (e.g.,driver or passenger), etc. For example, a driver may be provided withaccess to applications/features that will minimize driver distraction,while a passenger may be provided with access to a greater range ofapplications/features.

In one embodiment, system and methods for collecting driver biometricsare disclosed. In one embodiment, driver behavioral profile data may becollected through vehicle sensors. Examples of such sensors includesteering wheel sensors (e.g., hand position, pressure, etc.),handwriting sensors, touchpad sensors, fingerprint sensors, pedalpressure/timing sensors, front camera and impulse sensors, manual shiftsensors, seat weight sensors, driver camera sensors, etc. This data maybe combined with other modalities (e.g., voice recognition, etc.) formulti-modal security.

In one embodiment, data from various sensors may be integratedtemporally. The resulting data may be analyzed for driver biometricsfeatures (e.g., how the driver combines wheel, pedal, and shiftingmovements precisely in time, which may differentiate the driver fromothers).

In one embodiment, the sensors may detect fine motor skill movements,coarse motor skills movements, and event-driven response and behavioralpatterns.

In one embodiment, data from additional equipment (e.g., monitoringequipment such as that used by insurance companies to monitoringdriving) may be combined for impulse responses, driving behavior, etc.

In one embodiment, a driver may be authenticated while driving withoutany distractions. For example, the driver may not be required to enterpasswords, PINs, etc. to be authenticated.

In one embodiment, the authentication information may be used to grantthe driver access to the vehicle wallet.

Referring to FIG. 1, a method for driver authentication through embeddedsensing is disclosed. User 115 may interact with vehicle 110, which maybe a “smart vehicle.” As used herein, the phrase “smart vehicle” mayrefer to a vehicle having built-in sensors, with added sensors,additional devices (e.g., mobile devices), etc. that may be able tosense or detect one or more characteristics of a person. Examples ofsuch vehicles include cars, motorcycles, boats, airplanes, trains, etc.A smart vehicle or the systems/devices that typically accompany such avehicle may be used to coordinate a user's interaction with adrive-through interface, such as a drive-through ATM, an in-persontransaction, etc.

Sensors in vehicle 110 may collect biometric data from user 115, such asuser 115's weight, facial characteristics, iris characteristics,fingerprint data, voice data, etc. Sensors may further detect user 115'sinteraction with vehicle 110, including hand movements, pedal movements,etc. Sensors may also detect user 115's responses to traffic conditions,driving habits, etc. Sensors may further detect user inputs through avariety of input devices.

Sensors may also collect data regarding vehicle 110, such as vehicle110's position, speed, behavior in traffic, etc.

Any sensor or device that collects data about or from user 115 may beused as necessary and/or desired.

Trusted vehicle system 105 may use the data from the sensors toauthenticate the user. In one embodiment, trusted vehicle system 105 maybe an application that is nm by vehicle 110's control systems. Trustedvehicle system 105 may be unlocked and activated through user input,such as biometric, behavioral, etc. In one embodiment, trusted vehiclesystem 105 may also be activated by, for example, hardware tokens. Thisseparation and dedicated hardware unit may provide an additional levelof security by using biometric-activated processing of data, fullencryption, and separation from other non-trusted and potentiallymalicious applications that might reside in the regular system. Trustedcommunication system may encrypt and send/receive data from a financialinstitution or other institution/entity.

In one embodiment, financial services grade authentication may be used.The data may be protected both during transmission and during storage.

In one embodiment, mobile device 120, which may be registered to user115, may collect some or all of this data, and may communicate this datato vehicle 110 or server 155 through network 150.

In another embodiment, a combination of sensors in vehicle 110 andmobile device 120 may be used.

Vehicle 110 and/or mobile device 120 may include a wallet application(not shown) that may store data regarding at least one financialinstrument that may be used to conduct a transaction.

Server 155 may receive and process data received from vehicle 110 andmobile device 120. In one embodiment, server 155 may communicate thecollected data, payment data, or other information to at least oneentity with which user 115 wishes to conduct a transaction. Exampleentities include financial institution 160, automated teller machine(ATM) 170, drive-through service 180, and toll 190. These entities areexemplary only, and it should be recognized that other entities mayparticipate as is necessary and/or desired.

Referring to FIG. 2, a flowchart depicting a method for driverbiometric-based authentication according to one embodiment is provided.

In step 205, a wallet may be established for a trusted vehicle. In oneembodiment, the vehicle wallet may be limited to external fund sources,trusted vehicle security features, such as GPS tracking systems,security tokens, etc.

In step 210, an individual driver profile may be created. In oneembodiment, the driver profiles may be created using password and/or PINbased authentication, driver identification, key-based identification,other biometric identification (e.g., facial recognition, voicerecognition, etc.), or any other suitable technique or combination oftechniques.

In step 215, an individual driver profile for a shared vehicle walletmay be established. In one embodiment, this may include setting spendinglimits, usage terms, authentication requirements, etc.

In step 220, individual driver profiles may be linked to one or morewallet. In one embodiment, the one or more wallet may reside on, forexample, an electronic device for the driver, and that wallet mayallocate funds to the vehicle wallet.

In step 225, if there is an incoming request, in step 230, theauthenticity of the incoming request is confirmed and securityspecifications may be acquired from the driver. For example, the drivermay specify anonymous payments, payments through the vehicle wallet,payments through a mobile device wallet, payments from bank account viaa linked vehicle wallet, etc.

In step 235, corresponding driver accounts may be scanned and a paymentmechanism selection may be confirmed by the driver.

In step 240, the payment may be made through the vehicle wallet.

Referring to FIG. 3, a method for ongoing authentication is providedaccording to one embodiment.

In step 305, driver motor skill data may be collected from, for example,vehicle sensors. For example, sensors may be provided on the steeringwheel, pedals, seats, transmission, etc. In addition, cameras and/ormicrophones may be provided.

Examples of driver motor skill data that may be collected includessteering wheel activity (e.g., force applied, movement, etc.), pedalactivity (e.g., movement, pressure, transition between pedals, etc.),manual transmission activity (e.g., pressure, shift patterns, shiftpoints, etc.), seat activity (e.g., driver weight, seat position, etc.),driver eye activity, responsiveness to road conditions (e.g., lanetracking, distance from other vehicles), vehicle speed activity (e.g.,acceleration, braking, average speed, etc.), vehicle interior volume(e.g., radio volume level, radio stations listened to, etc.), vehiclelocation data (e.g., routes travelled), hand/arm movements and/orgestures, eye movement patterns, any actions used to control the system,data acquired from other devices and/or systems, and any otherbehavioral activities as is necessary and/or desired.

After being collected, the data may be “integrated.” In one embodiment,the collected data may be related to each other in the time domain. Forexample, if the user performs multiple tasks (e.g., clutch, shift,release clutch gas), how these multiple input patterns overlap with eachother is important. Integrated markers may be extracted from themultiple input data sources. Other patterns, such as voice, language,etc. may be integrated with other data.

In step 310, fused driver motor skill features may be extracted from thedriver motor skill data. Fused driver motor skill features are more thanone motor skill that are related in time. For example, the timing anddata collected when a driver depresses the clutch, shifts gears, andreleases the clutch may be extracted. The transition from the gas pedalto the brake pedal may be extracted. The driver's response to anexternal stimulus (e.g., road hazard, stop lights, etc.) may beextracted. Other examples include, eye movements, facial expressions,spoken language, voice recognition, etc.

In step 315, the collected data may be integrated with real-time trafficand/or road sensor data to extract driver response patterns. Forexample, average road speeds sensed by traffic sensors or drivermonitoring devices may be integrated with sensed vehicle speeds andother vehicle data. Examples include how the driver responds to trafficsignals, how the user reacts to stop signs, how the user brakes, how thedriver responds to traffic situations, etc. Data may also be sensed fromtraffic cameras, video recordings, images, etc.

In one embodiment, data may be sensed from on-board vehicle safetyequipment. In one embodiment, this equipment may monitor vehicle speeds,following distances, etc.

In step 320, a driver profile may be created based on the motor skilldata and the behavioral response. In one embodiment, the collected datafrom multiple sources may be analyzed, the unique identifiers/markersmay be extracted from the data.

Referring to FIG. 4, a method of authenticating a driver using abehavioral profile is disclosed according to one embodiment. In step405, sensor data for a current driver may be collected. In oneembodiment, motor skill data, fused data, and impulse response data maybe collected.

In step 410, the collected data may be compared to the profile. In oneembodiment, more than one profile may be stored on a vehicle. In anotherembodiment, the profile may be maintained on a device, such as aportable electronic device.

In step 415, if the collected data matches the collected data, thedriver may be authenticated based on the behavioral data collected. Thecollected data may be integrated with other authentication modalities,including, for example, facial biometrics, voice biometrics, fingerprintbiometrics, PIN and/or passwords, key token authentication, etc.

If, in step 420, the collected data does not match the profile, thedriver may be requested to provide explicit authentication.

In step 425, once the driver is authenticated, the driver may be grantedaccess to the vehicle wallet or any other desired wallet, account,activities, etc. that may be authenticated based on driver behaviors.

In one embodiment, the authentication may be used to grant the driveraccess to physical areas, such as garages, parking areas, restrictedareas, controlled-access highways, etc.

In another embodiment, the authentication may be used to authenticatethe driver to another wallet, such as a mobile wallet on the driver'smobile device. Other identification, authentication and access may begranted based on the authentication as necessary and/or desired.

Hereinafter, general aspects of implementation of the systems andmethods of the invention will be described.

The system of the invention or portions of the system of the inventionmay be in the form of a “processing machine,” such as a general purposecomputer, for example. As used herein, the term “processing machine” isto be understood to include at least one processor that uses at leastone memory. The at least one memory stores a set of instructions. Theinstructions may be either permanently or temporarily stored in thememory or memories of the processing machine. The processor executes theinstructions that are stored in the memory or memories in order toprocess data. The set of instructions may include various instructionsthat perform a particular task or tasks, such as those tasks describedabove. Such a set of instructions for performing a particular task maybe characterized as a program, software program, or simply software.

In one embodiment, the processing machine may be a specialized computerprocessor.

As noted above, the processing machine executes the instructions thatare stored in the memory or memories to process data. This processing ofdata may be in response to commands by a user or users of the processingmachine, in response to previous processing, in response to a request byanother processing machine and/or any other input, for example.

As noted above, the processing machine used to implement the inventionmay be a general purpose computer. However, the processing machinedescribed above may also utilize any of a wide variety of othertechnologies including a special purpose computer, a computer systemincluding, for example, a microcomputer, mini-computer or mainframe, aprogrammed microprocessor, a micro-controller, a peripheral integratedcircuit element, a CSIC (Customer Specific Integrated Circuit) or ASIC(Application Specific Integrated Circuit) or other integrated circuit, alogic circuit, a digital signal processor, a programmable logic devicesuch as a FPGA, PLD, PLA or PAL, or any other device or arrangement ofdevices that is capable of implementing the steps of the processes ofthe invention.

The processing machine used to implement the invention may utilize asuitable operating system. Thus, embodiments of the invention mayinclude a processing machine running the iOS operating system, the OS Xoperating system, the Android operating system, the Microsoft Windows™ 8operating system, Microsoft Windows™ 7 operating system, the MicrosoftWindows™ Vista™ operating system, the Microsoft Windows™ XP™ operatingsystem, the Microsoft Windows™ NT™ operating system, the Windows™ 2000operating system, the Unix operating system, the Linux operating system,the Xenix operating system, the IBM AIX™ operating system, theHewlett-Packard UX™ operating system, the Novell Netware™ operatingsystem, the Sun Microsystems Solaris™ operating system, the OS/2™operating system, the BeOS™ operating system, the Macintosh operatingsystem, the Apache operating system, an OpenStep™ operating system oranother operating system or platform.

It is appreciated that in order to practice the method of the inventionas described above, it is not necessary that the processors and/or thememories of the processing machine be physically located in the samegeographical place. That is, each of the processors and the memoriesused by the processing machine may be located in geographically distinctlocations and connected so as to communicate in any suitable manner.Additionally, it is appreciated that each of the processor and/or thememory may be composed of different physical pieces of equipment.Accordingly, it is not necessary that the processor be one single pieceof equipment in one location and that the memory be another single pieceof equipment in another location. That is, it is contemplated that theprocessor may be two pieces of equipment in two different physicallocations. The two distinct pieces of equipment may be connected in anysuitable manner. Additionally, the memory may include two or moreportions of memory in two or more physical locations.

To explain further, processing, as described above, is performed byvarious components and various memories. However, it is appreciated thatthe processing performed by two distinct components as described abovemay, in accordance with a further embodiment of the invention, beperformed by a single component. Further, the processing performed byone distinct component as described above may be performed by twodistinct components. In a similar manner, the memory storage performedby two distinct memory portions as described above may, in accordancewith a further embodiment of the invention, be performed by a singlememory portion. Further, the memory storage performed by one distinctmemory portion as described above may be performed by two memoryportions.

Further, various technologies may be used to provide communicationbetween the various processors and/or memories, as well as to allow theprocessors and/or the memories of the invention to communicate with anyother entity; i.e., so as to obtain further instructions or to accessand use remote memory stores, for example. Such technologies used toprovide such communication might include a network, the Internet,Intranet, Extranet, LAN, an Ethernet, wireless communication via celltower or satellite, or any client server system that providescommunication, for example. Such communications technologies may use anysuitable protocol such as TCP/IP, UDP, or OSI, for example.

As described above, a set of instructions may be used in the processingof the invention. The set of instructions may be in the form of aprogram or software. The software may be in the form of system softwareor application software, for example. The software might also be in theform of a collection of separate programs, a program module within alarger program, or a portion of a program module, for example. Thesoftware used might also include modular programming in the form ofobject oriented programming. The software tells the processing machinewhat to do with the data being processed.

Further, it is appreciated that the instructions or set of instructionsused in the implementation and operation of the invention may be in asuitable form such that the processing machine may read theinstructions. For example, the instructions that form a program may bein the form of a suitable programming language, which is converted tomachine language or object code to allow the processor or processors toread the instructions. That is, written lines of programming code orsource code, in a particular programming language, are converted tomachine language using a compiler, assembler or interpreter. The machinelanguage is binary coded machine instructions that are specific to aparticular type of processing machine, i.e., to a particular type ofcomputer, for example. The computer understands the machine language.

Any suitable programming language may be used in accordance with thevarious embodiments of the invention. Illustratively, the programminglanguage used may include assembly language, Ada, APL, Basic, C, C++,COBOL, dBase, Forth, Fortran, Java, Modula-2, Pascal, Prolog, REXX,Visual Basic, and/or JavaScript, for example. Further, it is notnecessary that a single type of instruction or single programminglanguage be utilized in conjunction with the operation of the system andmethod of the invention. Rather, any number of different programminglanguages may be utilized as is necessary and/or desirable.

Also, the instructions and/or data used in the practice of the inventionmay utilize any compression or encryption technique or algorithm, as maybe desired. An encryption module might be used to encrypt data. Further,files or other data may be decrypted using a suitable decryption module,for example.

As described above, the invention may illustratively be embodied in theform of a processing machine, including a computer or computer system,for example, that includes at least one memory. It is to be appreciatedthat the set of instructions, i.e., the software for example, thatenables the computer operating system to perform the operationsdescribed above may be contained on any of a wide variety of media ormedium, as desired. Further, the data that is processed by the set ofinstructions might also be contained on any of a wide variety of mediaor medium. That is, the particular medium, i.e., the memory in theprocessing machine, utilized to hold the set of instructions and/or thedata used in the invention may take on any of a variety of physicalforms or transmissions, for example. Illustratively, the medium may bein the form of paper, paper transparencies, a compact disk, a DVD, anintegrated circuit, a hard disk, a floppy disk, an optical disk, amagnetic tape, a RAM, a ROM, a PROM, an EPROM, a wire, a cable, a fiber,a communications channel, a satellite transmission, a memory card, a SIMcard, or other remote transmission, as well as any other medium orsource of data that may be read by the processors of the invention.

Further, the memory or memories used in the processing machine thatimplements the invention may be in any of a wide variety of forms toallow the memory to hold instructions, data, or other information, as isdesired. Thus, the memory might be in the form of a database to holddata. The database might use any desired arrangement of files such as aflat file arrangement or a relational database arrangement, for example.

In the system and method of the invention, a variety of “userinterfaces” may be utilized to allow a user to interface with theprocessing machine or machines that are used to implement the invention.As used herein, a user interface includes any hardware, software, orcombination of hardware and software used by the processing machine thatallows a user to interact with the processing machine. A user interfacemay be in the form of a dialogue screen for example. A user interfacemay also include any of a mouse, touch screen, keyboard, keypad, voicereader, voice recognizer, dialogue screen, menu box, list, checkbox,toggle switch, a pushbutton or any other device that allows a user toreceive information regarding the operation of the processing machine asit processes a set of instructions and/or provides the processingmachine with information. Accordingly, the user interface is any devicethat provides communication between a user and a processing machine. Theinformation provided by the user to the processing machine through theuser interface may be in the form of a command, a selection of data, orsome other input, for example.

As discussed above, a user interface is utilized by the processingmachine that performs a set of instructions such that the processingmachine processes data for a user. The user interface is typically usedby the processing machine for interacting with a user either to conveyinformation or receive information from the user. However, it should beappreciated that in accordance with some embodiments of the system andmethod of the invention, it is not necessary that a human user actuallyinteract with a user interface used by the processing machine of theinvention. Rather, it is also contemplated that the user interface ofthe invention might interact, i.e., convey and receive information, withanother processing machine, rather than a human user. Accordingly, theother processing machine might be characterized as a user. Further, itis contemplated that a user interface utilized in the system and methodof the invention may interact partially with another processing machineor processing machines, while also interacting partially with a humanuser.

It will be readily understood by those persons skilled in the art thatthe present invention is susceptible to broad utility and application.Many embodiments and adaptations of the present invention other thanthose herein described, as well as many variations, modifications andequivalent arrangements, will be apparent from or reasonably suggestedby the present invention and foregoing description thereof, withoutdeparting from the substance or scope of the invention.

Accordingly, while the present invention has been described here indetail in relation to its exemplary embodiments, it is to be understoodthat this disclosure is only illustrative and exemplary of the presentinvention and is made to provide an enabling disclosure of theinvention. Accordingly, the foregoing disclosure is not intended to beconstrued or to limit the present invention or otherwise to exclude anyother such embodiments, adaptations, variations, modifications orequivalent arrangements.

What is claimed is:
 1. A system for driver authentication throughembedded sensing comprising: a vehicle comprising: a first sensorsensing a physical characteristic of a vehicle occupant; a second sensorsensing a vehicle interaction movement of the vehicle occupant that isassociated with the vehicle occupant's operation of the vehicle; atleast one computer processor executing a computer application, thecomputer application receiving the sensed physical characteristic andthe sensed vehicle interaction movement from the first sensor and thesecond sensor; and a vehicle communication interface that communicatesthe sensed physical characteristic and the sensed vehicle interactionmovement; a back-end server in communication with the vehiclecommunication interface that receives the sensed physical characteristicand the sensed vehicle interaction movement; and a plurality oftransaction locations in communication with the back-end server; whereinat least one of the back-end server and one of the plurality oftransaction locations authenticates the vehicle occupant based on thesensed physical characteristic and the sensed vehicle interactionmovement.
 2. The system of claim 1, wherein the characteristic is abiometric characteristic of the vehicle occupant.
 3. The system of claim1, wherein the vehicle interaction movement comprises at least one of asteering movement, an acceleration movement, and a braking movement. 4.The system of claim 1, wherein the second sensor senses a plurality ofvehicle interaction movements, and the computer application extracts atleast one fused motor skill from the plurality of sensed vehicleinteraction movements.
 5. The system of claim 1, wherein the pluralityof transaction locations are selected from the group consisting of anautomated location and a manned location.
 6. The system of claim 1,wherein the vehicle further comprises a memory, and the memory stores aprofile for the vehicle occupant based on at least one of the sensedphysical characteristic of the vehicle occupant and the sensed vehicleinteraction movement of the vehicle occupant.
 7. A method forestablishing a driver profile using a plurality of embedded vehiclesensors, comprising: receiving, from a first vehicle sensor in avehicle, a sensed physical characteristic for a vehicle occupant;receiving, from a second vehicle sensor in the vehicle, a sensed vehicleinteraction movement for the vehicle occupant that is associated withthe vehicle occupant's operation of the vehicle; and the at least onecomputer processor creating a vehicle occupant profile from the sensedphysical characteristic and the sensed vehicle interaction movement;wherein the user profile is used to authenticate the vehicle occupantfor a transaction.
 8. The method of claim 7, wherein the second sensorsenses a plurality of vehicle interaction movements, and the methodfurther comprises: the at least one computer processor extracting atleast one fused motor skill from the plurality of sensed vehicleinteraction movements.
 9. The method of claim 8, wherein the vehicleinteraction movement comprises at least one of a steering movement, anacceleration movement, and a braking movement.
 10. The method of claim8, wherein the vehicle interaction movement is associated withresponding to a traffic situation.
 11. The method of claim 7, whereinthe sensed physical characteristic and the sensed vehicle interactionmovement are collected during operation of the vehicle.
 12. A method forauthorizing a transaction, comprising: retrieving a vehicle occupantprofile for an occupant of a vehicle; receiving, from a first vehiclesensor in the vehicle, a sensed physical characteristic for the vehicleoccupant; receiving, from a second vehicle sensor in the vehicle, asensed vehicle interaction movement for the vehicle occupant that isassociated with the vehicle occupant's operation of the vehicle; atleast one computer processor authenticating the vehicle occupant bycomparing the sensed physical characteristic and the sensed vehicleinteraction movement to the retrieved vehicle occupant profile.
 13. Themethod of claim 12, wherein the second sensor senses a plurality ofvehicle interaction movements, and the method further comprises: the atleast one computer processor extracting at least one fused motor skillfrom the plurality of sensed vehicle interaction movements.
 14. Themethod of claim 12, wherein the vehicle interaction movement comprisesat least one of a steering movement, an acceleration movement, and abraking movement.
 15. The method of claim 12, wherein the vehicleinteraction movement is associated with responding to a trafficsituation.
 16. The method of claim 12, wherein the step ofauthenticating the vehicle occupant by comparing the sensed physicalcharacteristic and the sensed vehicle interaction movement to theretrieved vehicle occupant profile comprises: the at least one computerprocessor generating a sensed profile from the sensed physicalcharacteristic and the sensed vehicle interaction movement that arecollected during operation of the vehicle.
 17. The method of claim 12,wherein the sensed physical characteristic and the sensed vehicleinteraction movement are collected during operation of the vehicle. 18.The method of claim 12, further comprising: the at least one computerprocessor transmitting the authentication to a third party.
 19. Themethod of claim 18, further comprising: the at least one computerprocessor granting the vehicle occupant access to a vehicle wallet basedon a successful authentication; and the at least one computer processorconducting a transaction with the vehicle wallet.
 20. The method ofclaim 12, wherein the vehicle interaction movement comprises at leastone of a steering movement, an acceleration movement, and a brakingmovement.